Conversation
|
@tylerturdenpants is this the right way to do this? or are Modifiers classified as something else. Over at ember-codemods/ember-no-implicit-this-codemod#44, I changed some things in this commit: ember-codemods/ember-no-implicit-this-codemod@aebe3e4 🤷♂️ I thought I needed to add modifiers to get it working... but... now I don't know what I'm doing. lol. oh wait, yes I do. I need to remove the visitor assumption |
|
Ya, if it is a type we can get using the built in |
|
I’m going to try and add more test coverage. I could use the help tho! |
|
at the moment, this is not the right way to detect modifiers :) ember-codemods/ember-no-implicit-this-codemod@4dcb769
but, in this case, since modifiers should be a built in type, we want it to be part of the default, yeah? |
I think so. Modifiers should have |
|
We might have to detect based on module path alone 🤔. Modifiers could be a class or a POJO, don’t have to extend from a common base class, etc. I think longer term Ember should expose the |
|
I meant to debug this and see if I could detect what modifiers were -- if it has to be on path - that's fine. Last I got stuck, I needed to look up how to debug inside puppeteer. Haven't done that yet. 🙃 |
|
@NullVoxPopuli I can help you today if you want |
… happens to have an EmberObject as its ancestor, that is not detected. It seems only native classes are detected right now
yeah, probably |
It's in there ;) |
ez.
no existing tests to draw off of for how to test that this actually works. So my test was/is if this PR passes: ember-codemods/ember-no-implicit-this-codemod#44
except... I couldn't get it failing first... wuuuuutt